home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware Game Pak
/
Shareware Game Pak For Windows.iso
/
aotd555d
/
install.doc
< prev
next >
Wrap
Text File
|
1992-02-21
|
9KB
|
207 lines
╒══════════════════════════════════════════════╕
│ ARM OF THE DRAGON, Third Edition │
│ Volume I of the Wars for Domination in 3045+ │
╞══════════════════════════════════════════════╧═════════════╕
│ By Steven H. Lin │
│ Original Program Concept by DevPalProj Team #1 │
│ BattleTech(tm) Concept by FASA Corporation │
│ Copyright 1990, 1991 by Steven H. Lin. All Rights Reserved │
╞════════════════════════════════════════════════════════════╧══════════════╕
│ Arm of the Dragon(tm) and AotD(tm) are trademarks of Merchant Prince Pro- │
│ ductions, Inc., registered in the U.S. Patent and Trademark Office. │
╞═══════════════════════════════════════════════════════════════════════════╡
│ BattleTech(tm) is a trademark of FASA Corporation, registered in the U.S. │
│ Patent and Trademark Office. │
╘═══════════════════════════════════════════════════════════════════════════╛
INSTALLATION GUIDE for AotD/3 Release 2
"Hey, what do you mean, 'This isn't what I thought
it'd be?'"
___Quick Notes______________________________________________________________
At this time, these installation docs pertain to AotD/3 Release 2, v5.55a.
Registered sysops will have received their specially-made "key" files that
will function with this, and subsequent, AotD/3 releases. This IS the
Release 2 that everybody has been waiting for: it's still looking better
and better, and more enhancements are making their way into the new source
even now.
As you may know by now, registered AotD sysops are able to access new re-
visions before anyone else. There often are new revisions and bug fixes
available ONLY to registered AotD sysops, as well as a potpourri of special
additions, modifications, and supplemental products, such as utilities and
other DOORs. If you wish to support the shareware concept, or want to have
access to more than just the basics, register AotD today!
Also: if you have questions, comments, suggestions, contact me ASAP! I'd
love to hear from you. If you need to, call me voice at 305/899-0957. Uh, no
collect calls, however. Or, if you want to call my BBS, the number is
305/899-1841, 2400 baud and higher, supporting both HST and v.32 banners.
___Modemland Surgeon General's Remarks______________________________________
WARNING: If you choose to run AotD/3 on your computer, you do so at your own
risk. Steven H. Lin, [The Deviant's Palace], and DevPal MetroNet Communi-
cations are not responsible for any mishaps which may occur while operating
this software. This software is presented as-is, although PKware's Authenti-
cation Verification scheme is used to protect all copies released directly
from DevPalMiami, the headquarters for AotD development.
___Installation Guide_______________________________________________________
1. Unarchive the AOTD archive file into the directory UNDER which you wish
to place the AotD/3 directory. (ie. the directory to be immediately ABOVE
the AotD/3 directory!)
2. After completely reading and understanding this document and AOTDSYSP.Doc,
execute the INSTALL.Bat file. INSTALL.Bat will set up AotD/3 properly in a
directory called AOTD directly underneath your present directory. It will
also generate special subdirectories under the AOTD directory.
2a. AotD/3 is NOT downwardly compatible with AotD/2! The data structures were
extensively redesigned to combat a severe dynamic memory allocation problem.
The differences between AotD/2's and AotD/3's data structures are too in-
credibly massive to allow for even a data conversion program to retool.
3. Set up your BBS to handle AotD/3. Generate whatever entry menus and
guides you need on your BBS system.
4. Here's the difficult part: designing the proper command line to invoke
AotD/3 on your BBS. However, this step is actually pretty easy to understand
if you're familiar with the Mycroft standard interface for DOORs. Basically,
AotD/3 follows the Mycroft interface! =(:->)
Some possible command lines ---
a. AOTD
Local operation
b. AOTD <node> <path to DOOR info file> RBBS
RBBS-PC operation (DORINFO<node>.Def)
A sample command line for a 1-node RBBS-PC system:
AOTD 1 K:\RBBS RBBS
c. AOTD <node> <path to DOOR info file> QBBS
QuickBBS operation (DORINFO1.Def)
A sample command line for a QuickBBS system:
AOTD 1 H:\QUICK QBBS
A sample batch file inclusion for a QuickBBS system:
:AotD
J:
CD \DOOR\AOTD
AOTD 1 H:\QUICK QBBS
H:
CD \QUICK
goto RelogQuick
d. AOTD <node> <path to DOOR info file> PCBOARD
PCBoard 12.0 operation (PCBOARD.Sys)
A sample command line for a 1-node PCBoard 12.0 system:
AOTD 1 F:\PCB PCBOARD
A sample batch file (AOTD) for a 1-node PCBoard 12.0 system:
J:
CD \DOOR\AOTD
AOTD 1 F:\PCB PCBOARD
F:
CD \PCB
Board
e. AOTD <node> <path to DOOR info file> PCBOARD14
PCBoard 14.0+ operation (PCBOARD.Sys)
A sample command line for a 1-node PCBoard 14.5 system:
AOTD 1 F:\PCB PCBOARD14
A sample batch file (AOTD) for a 1-node PCBoard 14.5 system:
J:
CD \DOOR\AOTD
AOTD 1 F:\PCB PCBOARD14
F:
CD \PCB
Board
e. AOTD <node> <path to DOOR info file> WILDCAT
Wildcat! <3.0 operation (CALLINFO.Bbs)
A sample command line for a 1-node Wildcat! 3.0 system:
AOTD 1 L:\WC WILDCAT
f. AOTD <node> <path to DOOR info file> WWIV
WWIV operation (CHAIN.Txt)
A sample command line for a WWIV system without the multi-
node modification:
AOTD 1 J:\IMS4 WWIV
A sample batch file (AOTD.Bat) for a WWIV system without the
multi-node modification:
J:
CD \DOOR\AOTD
AOTD 1 J:\IMS4 WWIV
J:
CD \IMS4
g. AOTD <node> <path to DOOR info file> GAP
GAP Communications, Wildcat! 3.0+, or DOOR.SYS operation
(DOOR.Sys)
A sample command line for a 1-node DOOR.SYS system:
AOTD 1 G:\TORC GAP
5. Check the NODES.BBS file to make sure things are properly set up. For
Mycroft DOORs, NODES.BBS is designed to handle a maximum of four nodes in
a BBS environment. Each of the four lines in NODES.BBS is merely a COM<x>
statement, where <x> represents a number from 1-4; each of these lines
is each of the nodes of your BBS. So, if you run a single-node BBS on COM2:,
then the file should look like:
COM2 <---- this is the important entry
COM<x>
COM<x> These other entries are not important!
COM<x>
5a. At this time, AotD/3 does not directly support multinode operation, al-
though many sysops have called in and told us that they have been able to
run AotD/3 successfully under a multinode setting.
___Assistance for Setting Up AotD/3_________________________________________
If you have problems setting up AotD/3 (and this should be a very RARE
situation), then all you have to do is link into the DevNet echo called
"AOTD".
What?!? You AREN'T connected to DevNet echos? None at all? =(:-<)
Well, here's how you can rectify the situation: Send a NetMail message to
FN 1:135/105, EN 50:5305/505, or WN 3519, containing the following
information:
1. Your real name
2. A telephone number that you can be reached at
3. Your address
4. Your BBS name and node number
5. An AreaFix password
6. A session password
You will be established as a DevNet participant within 24-72 hours and will
have all DevNet echos toggled on. Then all you have to do is periodically
poll FN 1:135/105 for your DevNet EchoMail packets (until we can move things
onto the backbone)!
NOTE: This does NOT mean that you are a registered AotD/3 sysop! See
AOTDSYSP.Doc for terms on registering AotD/3. If you enjoy AotD/3, please
register and reap the wonderful benefits of a registered sysop!